Columbia Kermit/kermit.zip/newsgroups/misc.19941031-19941221/[e-mail]_Mon Nov 28 14:46:15 1994.msg

Internet Message Format | 2020-01-01 | 4KB

Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA03353
  (5.65c+CU/IDA-1.4.4/HLK for <[e-mail]>); Mon, 28 Nov 1994 23:30:44 -0500
Received: by apakabar.cc.columbia.edu id AA18463
  (5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Mon, 28 Nov 1994 23:30:42 -0500
Path: news.columbia.edu!panix!news.mathworks.com!hookup!swrinde!cs.utexas.edu!news.cs.utah.edu!cc.usu.edu!jrd
From: [e-mail] (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: MSK 3.13 tektronics terminal emulation w/ vt320 mode.A
Message-Id: <[e-mail]>
Date: 28 Nov 94 20:46:15 MDT
References: <[e-mail]> <[e-mail]> <[e-mail]>
Organization: Utah State University
Lines: 50
Apparently-To: [e-mail]

In article <[e-mail]>, "John G. Miles" <[e-mail]> writes:
> Sorry if this is an obvious question, but I have been using
> MSKermit 3.13 on a 486/DX33 and often connect to my computer at the
> university to run graphics programs which support the tektronics
> graphics terminal.  If I set Kermit (before entering terminal mode)
> to emulate the tektronics terminal, then the graphics are displayed
> without problem.
>
> However, if I set my terminal to VT320 (which I
> prefer since I also use the Unix system extensively besides my
> graphics needs) and then enter terminal mode with the "c" command, the
> tektronics mode is *not* automatically invoked when the Unix box (an
> IBM RS/6000 system) starts sending the tektronics graphics commands.
> It *does* seem to try (i.e., I get the little square cursor), but
> immediately begins echoing the ascii text, itself, of the graphics
> commands.  Once I return to VT320 emulation mode, I no longer get
> anything readable, but rather my color monitor displays solid
> multi-colored gibberish (though I can tell that the keystrokes I type
> are still getting through to the Unix box).  I end up having to type
> "exit" as normal (even though the echo to my screen is the gibberish as
> indicated above) and redial the Unix box in VT320 mode.
>
> I've looked over the on-line documentation, and believe that I
> understand correctly the fact that the tektronics emulation is
> seemless when using the VT320 emulation mode.  But everything I've
> tried has been unsuccessful.
>
> Is it at all possible that the problem sits on my end (e.g., my video
> card which is a Trident SVGA)?  I'm not Kermit-proficient so any
> pointers, however basic, would be helpful.  Please e-mail me personally
> as well as posting to the newsgroup as I don't get to read the news as
> often as I'd like).
>
> --John Miles
> [e-mail]
----------
    I recall replying to you privately John.
    I can't help from the above description alone. The Kermit
documentation explains which commands in VT320 mode will trigger a
change to Tek mode, and it's a necessarily restrictive set. ESC Control-L
(ESCape Form Feed) is the most common mode, meaning Tek screen clear.
ESC [ ? 38 h  will too, as will starting a DEC Sixel graphics command.
    My suggestion is to capture a sample session to a log file via
LOG SESSION filename. Then send me the uuencoded file with commentary
on what should have happened when so I can dig into the bits.
    I will also repeat a warning which results from seeing those
funny colored blobs in VT320 mode. It is to never let anything use
video memory, A000-BFFF, because it's video territory. I will guess
that you may have let a memory manager sneak down there by mistake.
    Joe D.